Is there some way to lock editing of approved requirements

I have requirement states Draft/Proposed/Approved. Once a requirement is Approved, I want to make the object text and requirement state as read only and users should not be allowed to change the two. But users should be allowed to make changes to other attributes. Only some one with special previleges should be allowed to change state and object text of approved requirements. Any help on what can be done?
SystemAdmin - Mon Jul 12 03:54:20 EDT 2010

Re: Is there some way to lock editing of approved requirements
Ben_Sharples - Mon Jul 12 07:58:09 EDT 2010

You could define a trigger that fires when a user tries to edit the object text.

Within the dxl script that runs on trigger firing you would need it check the state of the object, and the current user to test if they are able to edit the object text.

If yes - output result is nothing - user will be unaware that anything has happened.

If no you can define pop-up message to inform user. Script then returns to module without allowing edit.
Other option which may take longer is to set up the module so that all data entry and modification is done via form entry, so that within DXL you can define whether a field on the DXL form is editable based on user and status sttribute - hence you never edit the data from the standard database view, only in configured DXL forms - which will take time to write

Re: Is there some way to lock editing of approved requirements
Mathias Mamsch - Mon Jul 12 10:24:03 EDT 2010

Ben_Sharples - Mon Jul 12 07:58:09 EDT 2010
You could define a trigger that fires when a user tries to edit the object text.

Within the dxl script that runs on trigger firing you would need it check the state of the object, and the current user to test if they are able to edit the object text.

If yes - output result is nothing - user will be unaware that anything has happened.

If no you can define pop-up message to inform user. Script then returns to module without allowing edit.
Other option which may take longer is to set up the module so that all data entry and modification is done via form entry, so that within DXL you can define whether a field on the DXL form is editable based on user and status sttribute - hence you never edit the data from the standard database view, only in configured DXL forms - which will take time to write

I think you cannot fully protect an object, eg from creating or deleting a link, deleting the object itself and purging it.

The only thing you could do is try to detect changes to an accepted object and then prevent saving the module altogether, but this is not only very awkward for the users but very complicated to program (detecting the changes!). Be aware that a simple attribute modification trigger might indeed not prevent important changes like drawing a link or deleting an object altogether.

If the approver had Admin access to the object you could make the trigger revoke DOORS access to the object for a certain group of users. Giving approvers this kind of access and using it for locking the DOORS object has implications (e.g. in shared edit or the rights to administrate attributes in the module).

Sorry I cannot offer any good solution for this.

Regards, Mathias


Mathias Mamsch, IT-QBase GmbH, Consultant for Requirement Engineering and D00RS

Re: Is there some way to lock editing of approved requirements
SystemAdmin - Tue Jul 13 01:26:29 EDT 2010

Thanks for the hints. I have installed 2 pre save triggers. One to not allow changes to object text if status is approved and other to disallow a group of users from changing the status from approved to anything else.

Re: Is there some way to lock editing of approved requirements
llandale - Tue Jul 13 14:48:28 EDT 2010

SystemAdmin - Tue Jul 13 01:26:29 EDT 2010
Thanks for the hints. I have installed 2 pre save triggers. One to not allow changes to object text if status is approved and other to disallow a group of users from changing the status from approved to anything else.

... and stop them from setting it Approved; save that for the QA folks.

Re: Is there some way to lock editing of approved requirements
SystemAdmin - Tue Jul 13 22:47:37 EDT 2010

llandale - Tue Jul 13 14:48:28 EDT 2010
... and stop them from setting it Approved; save that for the QA folks.

Thanks. that is an important control point that I missed.